Note
You will require a user with SYSDBA role to create schemas.
Note
The default Weblogic installation will be running JVM with 512MB, this has to be increased for the ADF managed server. Say, for a 2 CPU Quad Core with 16 GB it could have the JVM running at 8 GB as:
USER_MEM_ARGS="-Xms8192m –Xmx8192m -XX:PermSize=2048m -XX:MaxPermSize=2048m"
If the server is required to be running and access to command line needs to be returned use "nohup" and "&"
$ nohup ./startWebLogic.sh &
If the server is required to be running and access to command line needs to be returned use "nohup" and "&".
$ nohup ./$MW_HOME/user_projects/domains/<mydomain>/bin/startManagedWebLogic.sh {ManagedServer_name} {AdminServer URL} &
Assuming that OLL_MDS schema is created using Oracle Repository Creation Utility (RCU) as mentioned in Creating Schemas using Repository Creation Utility section, follow the below steps to create the repository.
Update the following parameters in JDBC data source connection pool:
Authentication order should be maintained as mentioned in the above screen. ‘OFSLLDBAuthenticator’ will be displayed as above.
Operation |
Default SQL Query from Weblogic |
Corresponding SQL Queries as per our Tables |
SQL Get Users Password: |
SELECT U_PASSWORD FROM USERS WHERE U_NAME = ? |
SELECT UAU_USR_PASSWORD FROM USER_AUTHORISATIONS WHERE UAU_USR_CODE = ? |
SQL Set User Password: |
UPDATE USERS SET U_PASSWORD = ? WHERE U_NAME = ? |
UPDATE USER_AUTHORISATIONS SET UAU_USR_PASSWORD = ? WHERE UAU_USR_CODE = ? |
SQL User Exists: |
SELECT U_NAME FROM USERS WHERE U_NAME = ? |
SELECT UAU_USR_CODE FROM USER_AUTHORISATIONS WHERE UAU_USR_CODE = ? |
SQL List Users: |
SELECT U_NAME FROM USERS WHERE U_NAME LIKE ? |
SELECT UAU_USR_CODE FROM USER_AUTHORISATIONS WHERE UAU_USR_CODE LIKE ? |
SQL Create User: |
INSERT INTO USERS VALUES ( ? , ? , ? ) |
INSERT INTO USER_AUTHORISATIONS(UAU_USR_CODE, UAU_USR_PASSWORD,UAU_DESC) VALUES(?,?,?) |
SQL Remove User: |
DELETE FROM USERS WHERE U_NAME = ? |
DELETE FROM USER_AUTHORISATIONS WHERE UAU_USR_CODE= ? |
SQL List Groups: |
SELECT G_NAME FROM GROUPS WHERE G_NAME LIKE ? |
SELECT UGR_GROUP_CODE FROM USER_GROUPS WHERE UGR_GROUP_CODE LIKE ? |
SQL Group Exists: |
SELECT G_NAME FROM GROUPS WHERE G_NAME = ? |
SELECT UGR_GROUP_CODE FROM USER_GROUPS WHERE UGR_GROUP_CODE = ? |
SQL Create Group: |
INSERT INTO GROUPS VALUES ( ? , ? ) |
INSERT INTO USER_GROUPS(UGR_GROUP_CODE,UGR_GROUP_DESC) VALUES(?,?) |
SQL Remove Group: |
DELETE FROM GROUPS WHERE G_NAME = ? |
DELETE FROM USER_GROUPS WHERE UGR_GROUP_CODE = ? |
SQL Is Member: |
SELECT G_MEMBER FROM GROUPMEMBERS WHERE G_NAME = ? AND G_MEMBER = ? |
SELECT UGM_MEMBER_USR_CODE FROM USER_GROUP_MEMBERS WHERE UGM_MEMBER_GROUP_CODE= ? AND UGM_MEMBER_USR_CODE = ? |
SQL List Member Groups: |
SELECT G_NAME FROM GROUPMEMBERS WHERE G_MEMBER = ? |
SELECT UGM_MEMBER_GROUP_CODE FROM USER_GROUP_MEMBERS WHERE UGM_MEMBER_USR_CODE= ? |
SQL List Group Members: |
SELECT G_MEMBER FROM GROUPMEMBERS WHERE G_NAME = ? AND G_MEMBER LIKE ? |
SELECT UGM_MEMBER_USR_CODE FROM USER_GROUP_MEMBERS WHERE UGM_MEMBER_GROUP_CODE= ? AND UGM_MEMBER_USR_CODE LIKE ? |
SQL Remove Group Memberships: |
DELETE FROM GROUPMEMBERS WHERE G_MEMBER = ? OR G_NAME = ? |
DELETE FROM USER_GROUP_MEMBERS WHERE UGM_MEMBER_USR_CODE= ? OR UGM_MEMBER_GROUP_CODE= ? |
SQL Add Member To Group: |
INSERT INTO GROUPMEMBERS VALUES( ?, ?) |
INSERT INTO USER_GROUP_MEMBERS (UGM_MEMBER_GROUP_CODE,UGM_MEMBER_USR_CODE) VALUES(?,?) |
SQL Remove Member From Group: |
DELETE FROM GROUPMEMBERS WHERE G_NAME = ? AND G_MEMBER = ? |
DELETE FROM USER_GROUP_MEMBERS WHERE UGM_MEMBER_GROUP_CODE= ? AND UGM_MEMBER_USR_CODE= ? |
SQL Remove Group Member: |
DELETE FROM GROUPMEMBERS WHERE G_NAME = ? |
DELETE FROM USER_GROUP_MEMBERS WHERE UGM_MEMBER_GROUP_CODE= ? |
SQL Get User Description: |
SELECT U_DESCRIPTION FROM USERS WHERE U_NAME = ? |
SELECT UAU_DESC FROM USER_AUTHORISATIONS WHERE UAU_USR_CODE = ? |
SQLSet User Description: |
UPDATE USERS SET U_DESCRIPTION = ? WHERE U_NAME = ? |
UPDATE USER_AUTHORISATIONS SET UAU_DESC= ? WHERE UAU_USR_CODE= ? |
SQL Get Group Description: |
SELECT G_DESCRIPTION FROM GROUPS WHERE G_NAME = ? |
SELECT UGR_GROUP_DESC FROM USER_GROUPS WHERE UGR_GROUP_CODE= ? |
SQL Set Group Description: |
UPDATE GROUPS SET G_DESCRIPTION = ? WHERE G_NAME = ? |
UPDATE USER_GROUPS SET UGR_GROUP_DESC= ? WHERE UGR_GROUP_CODE= ? |
Provider Name |
OFSLLDBAuthenticator |
|
Note
Application server needs to be restarted for these changes to take effect.
Create an OFSLL application super user to login to the application.
A script is provided in the distribution media in the dba_utils folder to create an user.
Note
By default there are no users created to login to OFSLL application.
Run the script ‘crt_app_user.sql script’ as a OFSLL application owner user.
The USERS are automatically mapped to default application group - OFSLL_USER.
Note
The Change Password feature uses the JMX Policy configured on the domain. Hence, the AdminServer is required to be up and running to enable this.
Note
If server is not restarted, JMX Policy Editor option will not appear